[js] hold BiDi numbers to their declared ranges - #18272

• Reject out-of-range BiDi numbers during both record construction and wire parsing.
• Enforce inclusive, exclusive, and alias-narrowed bounds across nested values.
• Add tests for boundary values, nullable fields, aliases, and union lists.

graph TD
  Constructor["Record constructor"] --> Validate["Validate value"] -->|alias| Resolve["Resolve alias"] --> Bounds{"Within bounds?"} -->|no| Error["ValidationError"]
  Wire["fromWire"] --> Validate
  Validate -->|primitive| Bounds
  Bounds -->|yes| Accepted["Accepted value"]

Loading

Keep bounds enforcement in the shared runtime validator. It covers inbound and outbound records, including nested lists and unions, without duplicating checks in generated types; validating resolved aliases before field-level bounds preserves both constraints.

Bug fix (1) +22 / -1

record.jsEnforce numeric bounds in shared record validation +22/-1

Enforce numeric bounds in shared record validation

• Adds inclusive and exclusive minimum and maximum checks for numeric values. Applies them to primitive nodes and, after validating a resolved alias, to bounds declared on the alias reference; failures include the field path in a ValidationError.

javascript/selenium-webdriver/bidi/serialization/record.js

Tests (1) +114 / -0

record_test.jsCover numeric boundaries in both validation directions +114/-0

Cover numeric boundaries in both validation directions

• Tests constructor and fromWire handling of alias ranges, narrowed alias fields, exclusive floating-point bounds, and numeric elements in union lists. Includes accepted boundary-adjacent values and nullable fields.

javascript/selenium-webdriver/test/bidi/serialization/record_test.js

💡 Did you know, you can copy the agent prompt from any finding and feed it to your IDE agent

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗